Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explicitly specified string must stay a string #431

Merged
merged 3 commits into from
Jan 3, 2020

Conversation

VitaliyKurokhtin
Copy link
Contributor

If string value was specified in YAML explicitly via quotes, or one of the other string syntaxes it must not be converted into any other type.

@VitaliyKurokhtin
Copy link
Contributor Author

@darrelmiller, please take a look.

@darrelmiller
Copy link
Member

Hey @VitaliyKurokhtin Thanks for the PR. Sorry it took so long for me to get around to looking at this. I am a bit concerned that we will lose the ability to represent DateTime values natively with this change. There's no choice but to explicitly quote them in when using JSON style and therefore DateTimes are always going to come back as strings. This isn't necessarily a terrible thing, but it would definitely be a breaking change.
I have no issue with treating quoted numbers and booleans as strings because JSON has a unquoted format for those.

@VitaliyKurokhtin
Copy link
Contributor Author

Good point. I'll make a change to bring back older behavior for DateTimes specifically.

@darrelmiller darrelmiller changed the base branch from master to vnext January 3, 2020 02:13
@darrelmiller darrelmiller merged commit 841b947 into microsoft:vnext Jan 3, 2020
@VitaliyKurokhtin VitaliyKurokhtin deleted the vvk/explicit-string branch February 19, 2020 01:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants